Hosting event-based applications

ABSTRACT

Media, methods, and systems are disclosed for hosting an event-based application. Application instructions corresponding to processing steps to be performed in response to particular events are received from a development environment. The events are associated with a group-based communication channel. An application comprising computer-executable instructions is generated based on the application instructions and metadata associated with the events. In response to detecting one or more of the events, execution of the computer-executable instructions is triggered. A response is received corresponding to output from applying the processing steps to the events. A message is posted into the respective communication channel corresponding to the response.

TECHNICAL FIELD

Embodiments of the invention relate to hosting event-based applications.More specifically, embodiments of the invention relate to enablingdeployment and hosting of event-based applications in connection withgroup-based communication systems.

The development, deployment, and hosting of event-based applicationsthat work in connection with group-based communication systems hastraditionally required a substantial amount of software developmentexperience and domain specific knowledge regarding application hosting.Such domain specific knowledge includes knowledge of an applicationprogramming interface of the group-based communication system, how todeploy and host an event-based application, and the complexitiesassociated with network connectivity between the group-basedcommunication system and an application execution environment onto whichthe event-based application is deployed. As a result, building, running,and maintaining a group-based communication system application requiresan experienced software developer with knowledge of the group-basedcommunication system as well as knowledge regarding applicationdeployment and hosting. This results in significant barriers to entry toassociated development platforms.

What is needed is a user-friendly platform for enabling deployment andhosting of event-based applications in connection with group-basedcommunications systems. Such a platform allows users withoutdomain-specific knowledge to deploy and host event-based applicationsinto an application execution environment and thereby reduces theabove-described barriers to entry.

SUMMARY

Embodiments of the invention address the above-identified problems byproviding a platform to build, run, deploy, and maintain event-basedapplications in connection with one or more group-based communicationsystems. In particular, in a first embodiment, the invention includesone or more non-transitory computer-readable media storingcomputer-executable instructions that, when executed by a processor,perform a method for hosting an application in connection with agroup-based communication system, the method comprising: receiving, froma development environment, application instructions and applicationconfiguration parameters associated with the application correspondingto processing steps to be performed in response to a plurality ofevents, and in response to detecting the one or more events of theplurality of events in the respective group-based communication systemchannel of the group-based communication system: triggering execution ofthe computer-executable instructions based on metadata associated withthe one or more events, posting, in the respective group-basedcommunication system channel, a message based on a response responsiveto the one or more events.

In a second embodiment, the invention includes a method for hosting anevent-based application in connection with a group-based communicationsystem, the method comprising: receiving, from a developmentenvironment, application instructions and application configurationparameters associated with the application corresponding to processingsteps to be performed in response to a plurality of events, and inresponse to detecting one or more events of the plurality of events in agroup-based communication system channel of the group-basedcommunication system: triggering execution of computer-executableinstructions based on metadata associated with the one or more events,posting, in the group-based communication system channel, a messagebased on a response responsive to the one or more events.

In a third embodiment, the invention includes a system comprising atleast one processor and at least one non-transitory memory storingcomputer executable instructions that when executed by the processorcause the system to carry out actions comprising: receiving, from adevelopment environment, application instructions and applicationconfiguration parameters associated with the application correspondingto processing steps to be performed in response to a plurality ofevents, and in response to detecting one or more events of the pluralityof events in a group-based communication system channel of thegroup-based communication system: triggering execution of thecomputer-executable instructions based on metadata associated with theone or more events, posting, in the group-based communication systemchannel, a message based on a response responsive to the one or moreevents.

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Other aspectsand advantages of the current invention will be apparent from thefollowing detailed description of the embodiments and the accompanyingdrawing figures.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

Embodiments of the invention are described in detail below withreference to the attached drawing figures, wherein:

FIG. 1 depicts an exemplary hardware platform for certain embodiments ofthe invention;

FIG. 2 depicts components of a system for carrying out embodiments ofthe invention;

FIG. 3 depicts a block diagram for carrying out embodiments of theinvention;

FIG. 4 depicts a user interface component for adding a workflow step incertain embodiments of the invention;

FIG. 5A depicts a user interface component for configuring arguments toa function in certain embodiments of the invention;

FIG. 5B depicts a user interface component for inserting a variableassociated with arguments to a function in certain embodiments of theinvention;

FIG. 6 depicts a data flow diagram for carrying out embodiments of theinvention; and

FIG. 7 depicts an exemplary flow chart for illustrating the operation ofa method in accordance with one embodiment of the invention.

The drawing figures do not limit the invention to the specificembodiments disclosed and described herein. The drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the invention.

DETAILED DESCRIPTION Context and Concepts of the Invention

As used herein, the term “group-based communication system” refers to acollaborative communication system used within an organization. In someembodiments, the group-based communication system is a channel-basedmessaging platform. Within the group-based communication system,communication may be organized into “channels,” each dedicated to aparticular topic or set of users. Channels are generally long-lasting,persistent discussions of a particular topic. Members of a particularchannel can post messages within that channel that are visible to othermembers of that channel together with other messages in that channel.Users may select a channel for viewing in order to see only thosemessages relevant to the topic of that channel without seeing messagesposted in other channels on different topics. For example, a softwaredevelopment company may have different channels for each softwareproduct being developed, where developers working on each particularproject can converse without bothering (or being bothered by) developersworking on other projects. Because the channels are generally persistentand directed to a particular topic or group, users can quickly andeasily refer back to previous communications for reference.

Communication data within a group-based communication system may includemessages, queries, files (e.g., documents, spreadsheets, computer code,images, video, audio, and/or electronic contact information), mentions,users or user profiles, interactions (e.g., reactions, edits, deletions,and/or prioritizations such as by pinning or starring), tickets,channels, applications integrated into one or more channels,conversations (e.g., groups of messages that have been segmented assingle units), workspaces (e.g., sets of channels, users, projects,tasks within an organization that may have their own sets of permissionsand that may be organized substantially in line with an organizationchart in some instances) or other data generated by or shared betweenusers of the group-based communication system that are associated withan organization's communication data using the group-based communicationsystem.

In some instances, the communication data may comprise data associatedwith a user (e.g., a user profile), including, but not limited to, auser identifier, one or more communication channel identifiersassociated with communication channels to which the user has beengranted access, one or more group identifiers for groups (ororganizations, teams, entities, or the like) with which the user isassociated, an indication of whether the user is an owner or manager ofany communication channels, an indication of whether the user has anycommunication channel restrictions, a plurality of messages, a pluralityof emoji, a plurality of conversations, a plurality of conversationtopics, an avatar, an email address, a real name (e.g., Austin Author),a username (e.g., austin_a), a password, user preferences and/orsettings, a time zone, a status, a token, and other user-specificinformation. In some embodiments, the group-based communication systemmay additionally or alternatively store permissions data associated withpermissions of individual users of the group-based communication system.In some embodiments, permissions associated with an individual user canbe mapped to, or otherwise associated with, an account or profileassociated with user data. Permissions can indicate which users cancommunicate directly with other users, which channels a user ispermitted to access, restrictions on individual channels, whichworkspaces the user is permitted to access, and restrictions onindividual workspaces, for example. In some embodiments, the permissionscan support the group-based communication system by maintaining securityfor limiting access to a defined group of users. In some suchembodiments, such users can be defined by common access credentials,group identifiers, or other criteria, as described above.

In some embodiments, the group-based communication system can bepartitioned into different workspaces, which can be associated withdifferent groups of users. Each workspace can be associated with a groupidentifier and one or more user identifiers can be mapped to, orotherwise associated with, the group identifier. Users corresponding tosuch user identifiers may be referred to as “members” of the group. Aworkspace may comprise one or more channels that are unique to thatworkspace and/or one or more channels that are shared between one ormore workspaces. In some embodiments, workspaces can be associated withone or more organization identifiers, which can be associated withorganizations or other entities associated with the group-basedcommunication system. In some embodiments, such data can be mapped to,or otherwise associated with, other types of data (e.g., user data,permission data, or channel data).

In order to expand the functionality of a group-based communicationsystem event-based applications are developed to integrate group-basedcommunication system functionality with external platforms. In someembodiments, an event-driven application development and hostingplatform is provided. Application developers author code to build andhost applications in connection with the group-based communicationsystem. In some embodiments, a command line interface is provided fordevelopers to quickly create cloud-based, event-driven applications thatare then deployed to an application execution environment associatedwith the group-based communication system.

In some embodiments, the event-driven application development andhosting platform can be utilized in connection with a workflow builderuser interface to build an event-based application without the need toauthor program code. In such embodiments, an event-based application maybe built by a user that understands a workflow, but does not havetraining or otherwise does not wish to author code. In otherembodiments, aspects of the event-driven application development andhosting platform are provided to trained software developers, whoimplement an event-based application by authoring code to implement theapplication logic.

In some embodiments, a set of application development tools are providedin the form of a command line interface (CLI). This CLI providesfunctionality to authenticate a developer's identity to the applicationdevelopment platform. In one embodiment, the developer invokes the CLIwith a parameter of “whoami” to determine whether the developer has beenpreviously authenticated. If the developer has been previouslyauthenticated as a particular user, the CLI with the “whoami” parameterwill return a username which is already authenticated. If the developerhas not been previously authenticated, the CLI may provide an errormessage to the effect that the CLI session has not been authenticated.

The developer may then invoke the CLI with a parameter of “login” toprovide authentication credentials or “logout” to log out of the CLIsession. In this embodiment, when the developer invokes the CLI with the“login” parameter, the CLI generates a command that can be cut andpasted to be executed in an authenticated session of a group-basedcommunication system. The generated command includes a ticket, whichincludes a unique, random number expressed as a hexadecimal string thatis valid only for a number of minutes. When the developer pastes thegenerated command into the authenticated client interface of thegroup-based communication system, authentication tokens are generatedthat are used to authenticate the hosted application both for deploymentas well as execution.

Once a developer is authenticated, the developer can build a projectfrom scratch, check out a project from a source code repository, or usethe CLI to populate a predefined project skeleton. A predefined projectskeleton is based on a pattern of different types or categories ofapplications that a developer is likely to need to build. In someembodiments, a suite of predefined project skeletons are made availablethrough the CLI by a provider of the application development platform. Adeveloper can initiate a command through the CLI to build a skeleton appcorresponding to the general type of app the developer is intending tobuild. From there, the developer can edit and extend the skeleton app tobuild out the specific functionality specified in the requirements ofthe application on which the developer is working.

In one embodiment, to initialize a new empty project, the developerinvokes the CLI with a parameter of “new.” This creates the most basicapplication framework with a set of minimal initialized configurationfiles and source code files containing example code, which is commentedout in some embodiments. In some embodiments, the developmentenvironment is Node.js, with configuration files being provided in ahuman-readable data serialization language format such as YAML. In someother embodiments, alternative programming languages are provided suchas Python or Golang.

Once the developer has edited the configuration files and added and/orupdated code in the source code files, the developer may deploy and runthe application to the event-based application hosting environment. Insome embodiments, the developer invokes the CLI with the CLI parameter“deploy” to deploy the application to the application executionenvironment associated with the hosting environment. In someembodiments, the developer may view logs associated with the CLI byinvoking the CLI with the parameter “activity.” In some embodiments, achronologically most recent portion of the logs can be viewed inconnection with the CLI parameter “activity—tail.” Once deployed, theapplication functionality is operable in the group-based communicationsystem user interface corresponding to the group-based communicationsystem associated with the runtime environment to which the applicationwas deployed. In some embodiments, the application can be undeployed orremoved from the execution environment using the CLI parameter “delete.”In this embodiment, the parameter “delete” does not delete theconfiguration and source code from the developer's developmentenvironment but rather un-deploys it from the application executionenvironment.

Such deployed applications may both implement group-based communicationsystem application functions as well as invoke group-based communicationsystem application functions associated with other deployedapplications. In some embodiments, such an application function is anatomic piece of application logic that can be reused. Broadly speaking,a function defines inputs, outputs, includes application logic togenerate the outputs from the inputs. In some cases, functionsadditionally perform certain specified functionality (also known as“side effects”) in addition to generating the outputs. For example, afunction post_message( )may have inputs including a message, a channelidentifier and a user identifier. The function application logic has aside effect of posting the provided message, attributed to the indicateduser, in the indicated channel, in the return values of “success” and“failure” indicating whether the message was successfully posted.

Generally, a function receives inputs and in response to these inputs,generates either of an error or outputs. The inputs may include any ofone or more arguments for the function, a name of the function, andother suitable information used to perform the function. The error maybe generated in response to a failure of the function. For example, if arequired argument is not provided within the inputs, the function mayfail and generate an error. The error may be returned to the group-basedcommunication system server and displayed as an error message on aclient device associated with the group-based communication system.Alternatively, outputs may be generated by the function in response to asuccessful execution of the function. In some embodiments, the outputs(and/or the error) may generate a success event (or, in the case of anerror, a failure event) on an event channel in the group-basedcommunication system, allowing users or automated processes to obtainresults. As discussed below, this also allows functions to be composedby having an event on the event channel to serve as a trigger conditionfor another function.

Alternatively, or in addition, in some instances, either of the outputsor the error may be sent directly to a subsequent function as inputarguments for the subsequent function. In some embodiments, the inputsmay be received as arguments to the function. Further, inputs may bereceived from the group-based communication system as message or eventinformation. In some embodiments, an undercurrent of data may beassociated with a particular channel of the group-based communicationsystem. The undercurrent of data includes various information associatedwith the group-based communication channel, such as, for example,metadata for messages posted within the channel, user informationassociated with users added to the channel, and channel information,such as the channel name and channel parameters. Accordingly, any of theinformation from the undercurrent of data may be sent as an argument forthe function. For example, a username and a time for a message may beused as arguments for a function to indicate which user sent the messageand the time that the message was sent. For example, a function iscontemplated that identifies the last user to post a message within thechannel.

In some embodiments, it may be desirable to utilize existing resourcesassociated with the group-based communication channel for the function.For example, channel related information and features such as accesscontrol, data scoping, subscriptions, application programming interfaces(API), data loss prevention integration, encryption key management, andinternational data residency integration may be called upon by thefunction to provide arguments or triggering events to initiate thefunction. Accordingly, the existing group-based communication channelmay be used as an event channel for the function, where events withinthe channel may trigger functions, such as, for example, sending amessage, adding a user, or reacting to a message. In some embodiments,any content published to the group-based communication channel may beused to trigger and supply arguments to a function.

In some embodiments, events may be published as event messages within achannel of the group-based communication system, where each eventmessage comprises metadata describing the event. Accordingly, functionscan be triggered based on events within the channel, as well as when anevent message is reacted to or commented on. In some such embodiments,it may be desirable to publish event messages such that the metadataassociated with the event message may be used to initiate and supplyinformation to a function. Alternatively, in some embodiments, it maynot be desirable to publish all events as event messages within thechannel, as doing so might cause users to receive too much unnecessaryinformation. Accordingly, event messages may be filtered such that onlycertain types of events are published as event messages. Alternatively,event messages may be published to the undercurrent of data for thechannel without being visible within the channel to users.

In some embodiments, the function is an object in the context of thegroup-based communication system, such as an object within anobject-oriented programming environment. Accordingly, the function maybe stored within a memory, such as a group-based communication systemdata store and associated with an identifier used to identify thefunction. Further, in some embodiments, the function may beauthenticated by any of the group-based communication system or anexternal application. In some embodiments, the function may beauthenticated in one authentication step that meets the authenticationrequirements of each of the group-based communication system, and theexternal application. Additionally, the function may be authenticatedalong with a user who initiated the function. Accordingly, embodimentsare contemplated where a user is authenticated by the group-basedcommunication system and the user does not need to perform furtheractions to be authenticated by an associated external application. Here,information relating to user authentication may be sent as an argumentfor the function, by way of a bearer token, for example. As such, if theuser is authenticated within the group-based communication system thenthe user can run a function in connection with an external application.A built-in function is an extension of the core functionality of thegroup-based communication system, a standard interface to the core APIof the group-based communication system.

In some embodiments, a workflow builder user interface is provided sothat users of a group-based communication system can build and extendevent-based applications without authoring code. The workflow builderuser interface may be used to automate processes into automatedworkflows in a group-based communication system. Workflows may be of anarbitrary complexity and may integrate with third-party applications andservices. In the context of a workflow, a trigger is what initiates aworkflow. Triggers may be automatically generated in response toarbitrary events in the group-based communication system matchingpre-specified conditions. Triggers may also be manually initiated, forexample by way of a user of a group-based communication systeminteracting with a shortcut menu that when selected will launch aworkflow. In some embodiments, a shortcut menu may be accessed from amenu in a group-based communication system channel.

A workflow may incorporate workflow steps. A workflow step is a unit ofexecution that performs an action such as sending a group-basedcommunication system message or causing a custom form user interfacecomponent to be presented to a user of a group-based communicationsystem. The execution logic corresponding to a workflow step may beexposed from within group-based communication system applications tointegrate a particular workflow with external systems (for example, byway of an API for example). When a user building a workflow inserts astep, the workflow-building user may configure one or more parameters topass along information to entered by end users of the workflow. Theworkflow-building user may employ a configuration modal dialog box toconfigure such behavior within the workflow. The configuration modaldialog box contains a set of fields. Each field in the configurationmodal dialog box allows the workflow-building user to define a sourcefor the input data that the workflow will consume as input. In someembodiments, the workflow-building user may insert variables surroundedby double curly brackets “{{variables}}” into a plain-text field toauto-populate output data from previous workflow steps.

In some embodiments, row-based and column-based objects are provided forpersisting data in connection with an event-based application consistentwith the present invention. In these embodiments, metadata associatedwith a data dictionary corresponding to the persisted data can beprovided in the configuration files of the event-based application. Inan exemplary embodiment, a table name is provided in the YAMLconfiguration file followed by a list of columns with a column name anda standard data type corresponding to each of the columns. In someembodiments, the standard data types include: (i) type “id” which is astring that uniquely represents a particular row in the persisted data;(ii) type “text” which corresponds to a UTF-8 encoded string of anarbitrary length; (iii) type “user” which corresponds to a uniquelydefined user identifier corresponding to a user of a group-basedcommunication system; (iv) type “channel” which corresponds to a channelin the group-based communication system; (v) type “date” taking the formof an ISO 8601 formatted string; and (vi) type “number” whichcorresponds to an integer or floating point number.

In some embodiments, data can be persisted and queried in connectionwith the data persistence service by making API calls to an API that isprovided in connection with code provided with the initial skeletonapplication provided by the application development platform. The datapersistence API may contain the below-described methods, which in someembodiments bear the prefix “apps.hosted.tables.” One method, named“putRow,” may be invoked to create or update a row when providing atable name and an object mapping of column name to value. If a rowhaving an “id” value corresponding to the “id” in the provided objectmapping, does not exist, a new row may be created. If a row having thecorresponding “id” value already exists in the persistent storage, therow having that “id” will be updated according to the values containedin the rest of the object mapping.

Another method, “getRow” may be invoked to retrieve a single row whengiven a table name and an “id” corresponding to the row that should beretrieved. Yet another method that may be provided is “deleteRow,” whichdeletes a single row, given a table name and a row “id.” Still anothermethod is “query,” which may be invoked to query a particular table andreturn a certain number of rows. The query expression may be any kind ofa query term that can be used to query a database, such as a query termthat can be used to query a SQL or NoSQL-type database. In someembodiments, there is a user interface component for interacting withand administering data that is persisted in the above-described manner.

Various categories of users and organizations interact with exemplaryevent-driven applications and associated application development,deployment, and hosting environments in several ways. The various typesof users and organization include (but are not limited to): (i) endusers of a group-based communication system, (ii) workflow users who usepre-built workflows associated with group-based communication systems;(iii) workflow-building users who build workflows to perform automatedfunctionality within a group-based communication system; (iv) users whocustomize group-based communication system functions and configureassociated triggers; (v) subscribing organizations of group-basedconfiguration systems that develop event-based applications by way ofgroup-based communication system functions to support automationrequired by the subscribing organization; and (vi) partner organizationsthat develop event-based applications and integrations to operate inconnection with group-based communication systems.

As a non-limiting example, an end user of a group-based communicationsystem in the course of using the group-based communication system mayuse a group-based communication system channel with interactivity toprovide feedback regarding a particular product. In so doing, the enduser decides that the end user would like to create a similar feedbackflow for other end users and other products. Using the group-basedcommunication system, the end user looks for a way to copy or use thesame or similar workflow. In this capacity, the end user becomes aworkflow user, who may wish to customize an existing workflow. Withinthe group-based communication system client interface, the end userturned workflow user begins a process of customizing the existingworkflow. The workflow user adds a solution based on an existingworkflow and customizes the new solution. The workflow user may then addthe customized solution to a particular group-based communication systemchannel. The workflow user may then send a message in-channel to letchannel members know about the new solution.

Channel members may provide comments regarding the new solution, andbased on those comments, the workflow user may update workflow solutionconfiguration by, for example, updating a question in a feedback formassociated with the solution.

In another example, while using a group-based communication system, aworkflow user may directly have the requirement for the workflow user'steam to have a way to review contracts. In this example, the workflowuser may browse the available workflows to determine whether an existingworkflow can be configured to be used by the team to review contracts.If an existing workflow can simply be configured to allow this, theworkflow user may configure and add a solution as described above.Alternatively, the workflow user may determine that no existing workflowexists to meet the needs of reviewing contracts. At this point theworkflow user may decide to build a suitable workflow, and the workflowuser takes on the role of workflow-building user. In this case, theworkflow-building user will open the workflow builder user interface andinitiate the process of creating a new workflow. In some embodiments,not all users have authorizations to create new workflows, and anadministrative user of the group-based communication system may have togrant permissions to the workflow-building user to create a newworkflow.

Once the workflow-building user has initiated the process of creating anew workflow in the workflow builder, the workflow-building user maybrowse workflow templates to determine whether an existing workflowtemplate exists to use as a basis to build the new workflow. If atemplate exists, the workflow-building user may open the template, add,modify or delete workflow steps, and define required inputs. If atemplate does not exist, the workflow-building user may opt to build aworkflow from scratch by adding workflow steps as needed and definingrequired inputs. In either case, the workflow-building user should thentest the newly created workflow by running the workflow and observingexecution based on a suite of test inputs. Finally, depending onadministrative configuration, the workflow-building user may choose topublish the workflow for some or all users of the group-basedcommunication system to use.

As a third example, a power user of a group-based communication systemmay encounter a requirement to initiate a technical support incidentwith a support ticket tracking system if an error rate in a supportedtechnical platform exceeds a certain error rate threshold. One optionfor the power user would be for the power user to browse availableworkflows and add a solution if such a solution exists already in thegroup-based communication system. As described above, this may involvesimply customizing a workflow as a workflow user or it may involvebuilding a workflow from scratch or based on a workflow template. If nosuch workflow functionality exists, the power user may determine that itis necessary to write code to implement a new event-based application.

In this case, the power user browses group-based communication systemfunctions either in the workflow browser or in a function browser orother source of function description documentation. Function descriptiondocumentation should provide a name of a function and a description ofinputs and outputs so that the power user, acting as a softwaredeveloper writing code, can write software code to access thegroup-based communication system function. In some embodiments, using afunction browser user interface associated with the group-basedcommunication system, the power user identifies a function entitled“Start Incident” that appears to provide necessary functionality toinitiate a technical support incident consistent with the power user'srequirements, In some embodiments, using the function browser userinterface, the power user select an option that allows the power user torequest permissions to build an application using the identifiedfunction. In this embodiment, an administrative user reviews the requestand decides whether to grant the power user permissions to build such anapplication.

If permission to build the application is obtained, the power user takeson the role of developer and, within an application developmentenvironment, uses a CLI as described above to initialize a newapplication skeleton. Next, the developer determines whether an existingtrigger may be leveraged. If no existing trigger is suitable, thedeveloper creates a new trigger. In the example of initiating a supportincident when an error rate in a supported technical platform exceeds acertain error rate threshold, the trigger may be the occurrence of anerror rate above the predefined error rate. Next, the developerconfigures the application and writes code necessary to invoke thefunction. In some embodiments, the developer optionally writes codeiteratively and tests the application locally within the developmentenvironment. Once the developer is ready to test the application in ahosted application execution environment, the developer may use the CLIto deploy the application to the application execution environment. Oncethe application is deployed, the developer may create an associatedworkflow that connects a trigger to a function in the deployedapplication. The developer may then configure an associated trigger(setting the error threshold, for example). In this example, theapplication is now live and when an error exceeds the configuredthreshold a support incident will automatically be initiated.

Within an organization that uses a group-based communication system,there may arise a requirement to manage different types of incidents.For example, physical security, emergencies, engineering support issues,and change requests may all be incidents to be managed separately. Anorganizational user may search available functions from third-partypartners to the operator of the group-based communication system todetermine whether any functions are available from third parties whoprovide integrations with an incident management system (or incidentmanagement systems) used by the organization. In some cases, an existingapplication will exist in a published application directory. If this isthe case, the organizational user can browse the functions and otherpublished documentation regarding the functions exposed by the publishedapplication. The organizational user may have to obtain requisitepermissions to initiate a new application or to otherwise create aworkflow and configure a trigger as described above. In this case, givenpermissions, the organizational user can configure the group-basedcommunication system to use the third party published application tointegrate with the incident management system according to theorganization's requirements.

On the other hand, if no suitable third-party partner integrationexists, the developer may choose to implement the integration directly.In this example, the developer would request administrative permissionsto build an application implementing a new function to carry out theintegration. In this embodiment, an administrative user reviews therequest and decides whether to grant the developer permissions to buildsuch an application implementing the specified function.

If permission to build the application is obtained, within anapplication development environment, the developer uses a CLI asdescribed above to initialize a new application skeleton. Next, in thisexample, the developer creates an “Alert User” function that contacts auser to be notified until the user to be notified acknowledges theincident or the incident times out. In this example, the developer alsocreates a “Start Incident” function. The developer then creates a newconfigurable trigger and deploys the application to a hosted applicationexecution environment. In some embodiments, the developer may configurethe developed group-based communication system function to be reusable(given proper permissions) within the developer's organization.

Finally, third-party partners of operators of group-based communicationsystems may wish to drive adoption of the partners' platforms by anexisting user base of users of the group-based communication system. Todrive such platform adoption, a partner may choose to develop andmaintain an event-based application hosted by the operator of thegroup-based communication system. The partner may receive requests fromits customers to utilize the partner's platform from a client interfaceof the group-based communication system. For example, in the case of apartner who is a provider of an incident management system, the partnermay have the requirement that its customers want to trigger, escalate,and resolve incidents from the client interface of the group-basedcommunication system.

In this example, a partner developer creates an application that is theofficial partner branded application for providing an integration withthe partner's application and/or platform. The partner user creates aconfiguration step to authenticate the group-based communication systemto the partner's application and/or platform. Next the partner developercreates a configuration step to map a particular group-basedcommunication channel to an application component such as, in thisexample, a group of users to be notified regarding a support incident.Next, the partner developer creates an integration function to implementintegration with the partner's application and/or platform using, forexample, an API exposed by the partner's application and/or platform. Insome embodiments, the function is hosted by the group-basedcommunication system operator. In some other embodiments, theintegration function is hosted remotely for example in connection with apublic or private cloud platform or in a data center maintained by thepartner. In some embodiments, the partner developer configures thefunction to be public and reusable and publishes it to a public orprivate application directory.

To secure access to sensitive information associated with an event-basedapplication running in connection with a group-based communicationsystem, a rich set of administrative functionality is advantageous.Hosted applications and corresponding functionality that may be utilizedby a broader set of users bring about potential data governanceconcerns, as providing additional data access and other functionalityincreases complexity of the overall group-based communication system,thereby raising potential issues regarding data security and compliance.

In some embodiments, administrative users of a group-based communicationsystem are able to manage roles corresponding to groups of users thatare authorized to develop, deploy, configure, modify and useapplications hosted in connection with group-based communicationsystems. Administrative users may specify which users are able to hostapplications in connection with a particular organization's group-basedcommunication system. Administrative users may allow a group or groupsof users to develop and deploy hosted applications in a safe, sandboxedenvironment without fear of data traveling outside the organization'sboundaries. In some embodiments, test data associated with a sandboxenvironment will be random data or data that is otherwise sanitized andde-identified of personally identifiable information or other sensitiveinformation. Administrative users may grant a group or groups of users“trusted” permission to deploy hosted applications that are capable ofcommunicating with systems that are external to a group-basedcommunication system, such as an organization's internal on-premisesenterprise applications or with other third-party, external systems.Furthermore, administrative users can themselves assign a group orgroups of users to be application hosting and/or application developmentplatform administrators.

In order to control data egress, administrative users can control whichapplications have the capability to make external API calls out tovarious destinations. These destinations include a particularorganization's internal, on premise systems and other third-party,external systems. Administrative users can specify a list of group-basedcommunication system OAuth scopes that are allowed for use in aparticular organization's hosted applications. Administrative users canlimit where a particular organization's hosted functions and/or triggerscan be made available to external organizations. Administrative userscan limit which group-based communication system workspaces within aparticular organization has access to specified hosted applications. Insome embodiments, administrative users may define required fields andvalues in the application configuration metadata of hosted applicationsto ensure that access control measures are not circumvented. For varioustypes of hosted applications, administrative users can choose whether aparticular hosted application should undergo validation before thehosted application is deployed.

Administrative users may have visibility into and a capability tomonitor a number and type of hosted applications, functions, and/ortriggers a particular organization is hosting as well as respectiveowners and/or collaborators who have access and authorization rights toparticular applications, functions, and/or triggers. Administrativeusers may audit the external functions and/or triggers that theirorganization is using as well as log data regarding inputs, outputs, andstate. Administrative users may detect and audit configuration changesto a particular organization's hosted applications. Administrative usersmay investigate resource consumption and gain insight into how much aparticular hosted application costs the organization to host.Administrative users may monitor usage and associated resourceconsumption of each hosted application and/or function. Administrativeusers may limit whether a particular organization's triggers may beinvoked from a particular webhook. Administrative users may audit whichexternal endpoints a particular organization's applications, functions,and/or triggers have called out to. Administrative users may audit whichcore group-based communication system API endpoints a particularorganization's functions have made calls out to. Administrative usersmay detect and audit changes to hosting roles and permissions.Administrative users may access source code on which a particular hostedapplication is based as well as respective source code control changehistory. Data governance principles are applied such data storagepractices are compliant with a particular organization's compliancestandards such as enterprise key management and international dataresidency.

Administrative users may grant to developers hosting-specific roles.Such roles correspond to a set of features that a particular developercan incorporate into the developer's hosted applications, functions,and/or triggers. In some embodiments, administrative users may createnew hosting permission roles and specify granular feature availabilityfor the new hosting permission roles. In one embodiment, three discreetroles are provided: basic, basic-plus-storage, and trusted. The basichosting permission role does not allow data storage. Applicationsassigned to the basic role (basic applications) may call built-ingroup-based communication system functions and group-based communicationsystem functions hosted by the same organization. The basic role may notcall out to external APIs. Functions implemented and exposed inapplications assigned to the basic role can be called by group-basedcommunication system workflows and other group-based communicationsystem functions hosted by the same organization. Basic applications maynot themselves be called by group-based communication system functionsowned by external organizations, and functions associated with basicapplications may not be called by a webhook that a basic applicationimplements. Applications that are assigned to the basic plus storagerole have the same characteristics as basic applications with theexception that they may store data. Applications that are assigned tothe trusted role (trusted applications) may store data and call and becalled the same as a basic application. In addition, trustedapplications may call out to external APIs. Trusted applications mayalso be called by group-based communication system functions owned byexternal organizations (implementing any necessary authentication andauthorization). Functions associated with trusted applications may alsobe called by a webhook that the trusted application implements.

In some embodiments, when a developer attempts to deploy an applicationwith features that are not authorized due to role-based authorizationconstraints configured in the application development environment or dueto otherwise implemented organizational rules, an error may be returnedto the developer, and the application will not be deployed. In someembodiments, a basic application may call a function exposed by atrusted application. In this embodiment, the basic application will needto provide any authentication credentials, such as a bearer token thatthe trusted application may require.

The subject matter of the invention is described in detail below to meetstatutory requirements; however, the description itself is not intendedto limit the scope of claims. Rather, the claimed subject matter mightbe embodied in other ways to include different steps or combinations ofsteps similar to the ones described in this document, in conjunctionwith other present or future technologies. Minor variations from thedescription below will be understood by one skilled in the art and areintended to be captured within the scope of the claimed invention. Termsshould not be interpreted as implying any particular ordering of varioussteps described unless the order of individual steps is explicitlydescribed.

The following detailed description of embodiments of the inventionreferences the accompanying drawings that illustrate specificembodiments in which the invention can be practiced. The embodiments areintended to describe aspects of the invention in sufficient detail toenable those skilled in the art to practice the invention. Otherembodiments can be utilized and changes can be made without departingfrom the scope of the invention. The following detailed description is,therefore, not to be taken in a limiting sense. The scope of embodimentsof the invention is defined only by the appended claims, along with thefull scope of equivalents to which such claims are entitled.

In this description, references to “one embodiment,” “an embodiment,” or“embodiments” mean that the feature or features being referred to areincluded in at least one embodiment of the technology. Separatereference to “one embodiment” “an embodiment”, or “embodiments” in thisdescription do not necessarily refer to the same embodiment and are alsonot mutually exclusive unless so stated and/or except as will be readilyapparent to those skilled in the art from the description. For example,a feature, structure, or act described in one embodiment may also beincluded in other embodiments but is not necessarily included. Thus, thetechnology can include a variety of combinations and/or integrations ofthe embodiments described herein.

Operational Environment for Embodiments of the Invention

Turning first to FIG. 1, an exemplary hardware platform for certainembodiments of the invention is depicted. Computer 102 can be a desktopcomputer, a laptop computer, a server computer, a mobile device such asa smartphone or tablet, or any other form factor of general- orspecial-purpose computing device. Depicted with computer 102 are severalcomponents, for illustrative purposes. In some embodiments, certaincomponents may be arranged differently or absent. Additional componentsmay also be present. Included in computer 102 is system bus 104, viawhich other components of computer 102 can communicate with each other.In certain embodiments, there may be multiple busses or components maycommunicate with each other directly. Connected to system bus 104 iscentral processing unit (CPU) 106. Also attached to system bus 104 areone or more random-access memory (RAM) modules 108. Also attached tosystem bus 104 is graphics card 110. In some embodiments, graphics card110 may not be a physically separate card, but rather may be integratedinto the motherboard or the CPU 106. In some embodiments, graphics card110 has a separate graphics-processing unit (GPU) 112, which can be usedfor graphics processing or for general purpose computing (GPGPU). Also,on graphics card 110 is GPU memory 114. Connected (directly orindirectly) to graphics card 110 is display 116 for user interaction. Insome embodiments no display is present, while in others it is integratedinto computer 102. Similarly, peripherals such as keyboard 118 and mouse120 are connected to system bus 104. Like display 116, these peripheralsmay be integrated into computer 102 or absent. Also connected to systembus 104 is local storage 122, which may be any form of computer-readablemedia and may be internally installed in computer 102 or externally andremovably attached.

Computer-readable media include both volatile and nonvolatile media,removable and nonremovable media, and contemplate media readable by adatabase. For example, computer-readable media include (but are notlimited to) RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, digital versatile discs (DVD), holographic media or otheroptical disc storage, magnetic cassettes, magnetic tape, magnetic diskstorage, and other magnetic storage devices. These technologies canstore data temporarily or permanently. However, unless explicitlyspecified otherwise, the term “computer-readable media” should not beconstrued to include physical, but transitory, forms of signaltransmission such as radio broadcasts, electrical signals through awire, or light pulses through a fiber-optic cable. Examples of storedinformation include computer-useable instructions, data structures,program modules, and other data representations.

Finally, network interface card (NIC) 124 is also attached to system bus104 and allows computer 102 to communicate over a network such asnetwork 126. NIC 124 can be any form of network interface known in theart, such as Ethernet, ATM, fiber, Bluetooth, or Wi-Fi (i.e., theInstitute of Electrical and Electronics Engineers (IEEE) 802.11 familyof standards). NIC 124 connects computer 102 to local network 126, whichmay also include one or more other computers, such as computer 128, andnetwork storage, such as data store 130. Generally, a data store such asdata store 130 may be any repository from which information can bestored and retrieved as needed. Examples of data stores includerelational or object oriented databases, spreadsheets, file systems,flat files, directory services such as LDAP and Active Directory, oremail storage systems. A data store may be accessible via a complex API(such as, for example, Structured Query Language), a simple APIproviding only read, write and seek operations, or any level ofcomplexity in between. Some data stores may additionally providemanagement functions for data sets stored therein such as backup orversioning. Data stores can be local to a single computer such ascomputer 128, accessible on a local network such as local network 126,or remotely accessible over public Internet 132. Local network 126 is inturn connected to public Internet 132, which connects many networks suchas local network 126, remote network 134 or directly attached computerssuch as computer 136. In some embodiments, computer 102 can itself bedirectly connected to public Internet 132.

Turning now to FIG. 2, an exemplary diagram illustrating components of asystem for carrying out embodiments of the invention is depicted andreferred to generally by reference numeral 200. System 200 provides aplatform for building, deploying, running, monitoring, and maintainingevent-based applications. System 200 includes any number of clientdevices such as group-based communication system client device 204,mobile client device 206, and developer client device 202.An individualuser may connect to components of system 200 using a single clientdevice or multiple client devices, either concurrently or sequentially.Similarly, in some embodiments, multiple users may share (concurrentlyor sequentially) a single client device to access the group-basedcommunication system. As depicted in FIG. 2, client devices may be anyform of computing device discussed above with respect to FIG. 1. Inparticular, a user may access components of system 200 using a desktop,a laptop, or a mobile device. Components of system 200 may be accessiblevia dedicated software of a particular client device or via a webbrowser associated with the client device. In some embodiments,developers and application hosting system administrators can accessadministrative functionality via any client device. In otherembodiments, administrative functions can only be accessed from alimited subset of client devices (for example, only via developer clientdevice 202). In some embodiments, group-based communication system 212is a channel-based messaging platform that can host a multiplicity ofgroup-based communication system servers and group-based communicationdata stores such as group-based communication system server 210 andgroup-based communication data store 208.

In some embodiments, group-based communication system 212 providesservices in connection with group-based communication system server 210.Group-based communication system server 210 may be a dedicated server, ashared server, a virtual machine instance in a cloud computingenvironment, or any other form of computing device discussed above withrespect to FIG. 1. Although a single group-based communication systemserver 210 is depicted, embodiments with multiple such group-basedcommunication system servers are also contemplated so as to providescale, redundancy and/or isolation between different instances of thegroup-based communication system. For example, a software developmentcompany may not wish to have its group-based communications systemhosted on the same server as a competitor's group-based communicationsystem for security reasons.

Cloud service provider 214 represents an on-demand cloud computingplatform providing data storage and computing resources in the form ofdedicated servers, shared servers, virtual machine instances in a cloudcomputing environment, or any other form of computing device discussedabove with respect to FIG. 1. Cloud service provider 214 may providesoftware as a service (SaaS), infrastructure as a service (IaaS) orplatform as a service services (PaaS), including serverless execution inan event-driven serverless execution environment. A serverless executionenvironment may enable the deployment of an application container thatis built for a particular execution environment. Broadly, an applicationcontainer is an isolated instance of a particular application includingapplication code, application configuration resources, and certainassociated libraries and application dependencies allowing rapid andindependent deployment of that application.

Server 210 is communicatively coupled to client devices 202, 204, and206 as well as cloud service provider 214 via network 216. Network 216may be a local area network (LAN), wide-area network (WAN), virtualprivate network (VPN) or the Internet. Broadly speaking, any type ofnetwork for providing communication between the various components ofsystem 200 is contemplated. Group-based communication system server 210may provide web server functionality to enable web-based clients andnon-web server functionality to enable clients using a dedicated app.Alternatively, both web-based clients and dedicated-app clients mightboth use a single web server, or the web server might be a gatewayproviding web-based access to the dedicated-app server. Other techniquesfor enabling communication among various types of client application arealso contemplated.

Group-based communication system data store 208 is communicativelyconnected to group-based communication system server 210. As depicted,group-based communication system data store 208 is directly connected togroup-based communication system server 210; however, any form ofcommunicative connection (for example, network-attached storage (NAS), anetwork file system (NFS), or cloud-based storage) can be employed.Broadly speaking, group-based communication system data store 208 storesthe all of the durable information used by group-based communicationsystem server 210. For example, group-based communication system datastore 208 may store all of the messages with their associated channels,documents and images uploaded to particular channels, channel membershipinformation, and/or user information. As previously discussed, multiplegroup-based communication system servers may be present in system 200.In such embodiments, each group-based communication system server mayhave its own copy of group-based communication system data store 208.Alternatively, multiple group-based communication system servers mayshare a single network-attached group-based communication system datastore. Alternatively, or in addition, in any of these embodiments, datamay be sharded across multiple group-based communication system datastores.

Turning now to FIG. 3, a block diagram for carrying out embodiments ofthe invention is depicted and referred to generally by reference numeral300. In various embodiments, triggers 302 are configured to triggerexecution of function 320. A trigger initiates application execution andmay take the form of a schedule 304, a webhook 306, a shortcut 308, or aslash command 310. In some embodiments, schedule 304 operates like atimer so that a trigger may be scheduled to fire periodically. In someembodiments, an end user of an event-based application sets an arbitraryschedule for the firing of a trigger, such as once-an-hour or every dayat 9:15 AM. Additionally, triggers 302 may take the form of webhook 306.Webhook 306 is a software component that listens at a webhook URL andport. In some embodiments, a trigger fires when an appropriate HTTPrequest is received at the webhook URL and port. In some embodiments,webhook 306 requires proper authentication such as by way of a bearertoken. In some embodiments, a payload associated with a particularwebhook invocation will contain information to be processed at thewebhook prior to causing any trigger to be fired. In some embodiments,one of the triggers 302 will fire any time webhook 306 is invoked andsome or all of the payload associated with a particular webhookinvocation will be passed on to one or more of functions 320. In someother embodiments, triggering will be dependent on payload content.

Another source of one of triggers 302 is a shortcut in shortcuts 308associated with a group-based communication system. In some embodiments,shortcuts 308 are global to a group-based communication system orspecific to a group-based communication system channel. Global shortcutsare not specific to a group-based communication system channel orworkspace. Global shortcuts may be initiated from a shortcuts button ina group-based communication message composer or from within a searchinterface associated with the group-based communication system clientinterface. Global shortcuts may trigger functions that are able toexecute without the context of a particular group-based communicationsystem message or group-based communication channel. By contrast,message- or channel-based shortcuts are specific to a group-basedcommunication system message or channel and operate in the context ofthe particular group-based communication system message or group-basedcommunication channel.

A further source of one of triggers 302 may be provided by way of slashcommands 310. Slash commands 310 may serve as entry points forgroup-based communication system functions, integrations with externalservices, or group-based communication system message responses. In someembodiments, slash commands 310 may be entered by a user of agroup-based communication system in order to trigger execution ofparticular application functionality. A particular slash command may beentered by a user of the group-based communication system directly intoa user input component ordinarily used to input group-basedcommunication system messages. In some embodiments, slash commands 310are distinguishable from a group-based communication system message inthat they are preceded by a forward slash (‘/’). Slash commands may befollowed by slash-command-line parameters which may be passed along toany group-based communication system function that is invoked inconnection with the triggering of a group-based communication systemfunction such as one of functions 320.

An additional source of triggers for a function is when an event (suchas event 312) matches one or more conditions as predetermined in asubscription (such as subscription 318). Events 312 may be subscribed toby any number of subscriptions 318, and each subscription may specifydifferent conditions and trigger a different function. In someembodiments, events are group-based communication system messages thatare received in one or more group-based communication system channels.App events 314 may be group-based communication system messages withassociated metadata that are created by an application in a group-basedcommunication system channel. Events 312 may also be direct messagesreceived by one or more group-based communication system users, whichmay be an actual user or a technical user, such as a bot. A bot is atechnical user of a group-based communication system that is used toautomate tasks. A bot may be controlled programmatically to performvarious functions. A bot may monitor and help process group-basedcommunication system channel activity as well as post messages ingroup-based communication system channels and react to members'in-channel activity. Bots may have names, profiles, profile photosassociated with a group-based communication system. Bots may bereferenced in group-based communication system messages and sent directmessages. Bots may be able to post messages and upload files as well asbe invited or removed from both public and private channels in agroup-based communication system.

Events 312 may also be any event associated with a group-basedcommunication system. Such group-based communication system events 316include events relating to the creation, modification, or deletion of auser account in a group-based communication system, events relating tomessages in a group-based communication system channel, such as creatinga message, editing or deleting a message or reacting to a message.Events 312 may also relate to creation, modification, or deletion of agroup-based communication system channel or the membership of a channel.Events 312 may also relate to user profile modification or groupcreation, member maintenance, or group deletion. Events 312 can also betriggered by a change detected by a third-party integration such as thechange in the status of a ticket within a third-partyincident-management system, for example.

As described above, subscription 318 indicates one or more conditionswhich, when matched by events, trigger a function. In some embodiments,a set of event subscriptions is maintained in connection with agroup-based communication system such that when an event occurs,information regarding the event is matched against a set ofsubscriptions to determine which (if any) of functions 320 should beinvoked. In some embodiments, the events to which a particularapplication may subscribe are governed by an authorization framework. Inone embodiment, the event types matched against subscriptions aregoverned by OAuth permission scopes which may be maintained by anadministrator of a particular group-based communication system.

Functions 320, which are triggered by triggers 302 and subscribed events312 may be provided in various forms. First, there are group-basedcommunication system “built-ins” 322, which are associated with the corefunctionality of a particular group-based communication system. Someexamples include creating a group-based communication system user orchannel. Next are builder “no code” functions 324 that may be developedby a user of a group-based communication system user in connection witha workflow builder user interface as described above. Finally, there arecode “hosted” 326 functions which are implemented by way of group-basedcommunication system applications that are developed as software code inconnection with a software development environment.

These various types of functions 320 may in turn integrate with APIs328. In some embodiments, APIs 328 are associated with third-partyservices that functions 320 employ to provide a custom integrationbetween a particular third-party service and a group-based communicationsystem. Examples of third-party service integrations include videoconferencing, sales, marketing, customer service, project management,and engineering application integration. In such an example one of thetriggers 302 could be a slash command 310 that is used to trigger a code“hosted” function 326, which makes an API call to a third-party videoconferencing provider by way of one of the integrated APIs 328. As shownin FIG. 3 the APIs 328 may themselves also become a source of one ormore triggers 302 or events 312. In this example, successful completionof a video conference could trigger a one of the functions 320 thatsends a message initiating a further API call to the third-party videoconference provider to download and archive a recording of the videoconference and store it in a group-based communication system channel.

In addition to integrating with APIs 328, functions 320 may persist andaccess data in tables 330. In some embodiments tables 330 areimplemented in connection with a database environment associated with aserverless execution environment in which a particular event-basedapplication is executing. In one embodiment, tables 330 may be providedin connection with a relational database environment. In otherembodiments, tables 330 are provided in connection with a databasemechanism that does not employ relational database techniques. As shownin FIG. 3, in some embodiments, reading or writing certain data to oneor more of tables 330, or data in table matching predefined conditionsis itself a source of one or more triggers 302 or events 312. Forexample, if tables 330 are used to maintain ticketing data in anincident-management system, then a count of open tickets exceeding apredetermined threshold may trigger a message being posted in anincident-management channel in the group-based communication system.

Turning now to FIG. 4, a user interface component for adding a workflowstep in certain embodiments of the invention is depicted and referred togenerally by reference numeral 400. In various embodiments, a corpus ofusable workflow steps is made available to a workflow-building user. Inone embodiment, search field 402 is provided so that theworkflow-building user may search for a particular workflow step by nameor by other characteristic of the workflow step which theworkflow-building user needs to perform a particular step within aworkflow. The workflow-building user may search for a workflow step interms of functionality or description of the workflow step, on the basisof an author of the workflow step, or a date range associated with thecreation or publishing of the particular workflow step.

In some embodiments, one or more of the listed available workflow stepsmay be added to a workflow by clicking an “Add” button associated withthe respective workflow step. As shown in the example of FIG. 4, variousworkflow steps may be provided. Workflow step 404 is a step thatperforms the function of creating a form, which will be displayed to anend user of a group-based communication system and made interactive foruse by the end user. Further configuration of workflow step (not shown)may be performed by the workflow-building user once theworkflow-building user has clicked to add workflow step 404 to theworkflow being built. Workflow step 406 is a step that performs thefunction of sending a message within the group-based communicationsystem. Workflow step 408 is a shortcut for implementing a group-basedcommunication system shortcut, which is a step that will execute theunderlying group-based communication system function associated with theshortcut as configured in the group-based communication system. Workflowsteps 404, 406, and 408 are shown to be from “GBCS Co.” which, in theillustrated embodiment, is an operator of a particular group-basedcommunication system. These workflow steps are said to be built-inbecause they are part of the core functionality of the group-basedcommunication system.

In some embodiments, to aid the workflow-building user in filteringavailable workflow steps, filter criteria are provided. Such filtercriteria include empty filter criterion 416 which provides a list of allsteps without limitation as indicated. Filter criteria also includefilter criterion 418, which limits the display to built-in workflowsteps that are provided by GBCS Co. In this embodiment, the filtercriteria also include filter criterion 420, which will limit the displayto workflow steps that are provided by a third-party application, suchas workflow steps 410 and 412, which provide the functionality of addingand deleting a spreadsheet row based on configuration of the workflowstep and any current state of the workflow up to that point.

Workflow step 414 is also a step that is exposed by a hosted group-basedcommunication system application that implements and exposes group-basedcommunication system functions within the workflow builder userinterface illustrated in FIG. 4. Workflow step 414 is entitled “Is HostUp” and is associated with the group-based application entitled “HostUp.” In various embodiments, the workflow-building user may interactwith user interface component 400 to filter displayed workflow steps toonly those provided by a particular third-party application suchapplication identifiers 422 and 424, which correspond to third-partyapplications “Spreadsheet for Workflow Builder” and “Host Up”respectively.

Turning now to FIG. 5A, a user interface component for configuringarguments to a function in certain embodiments of the invention isdepicted and referred to generally by reference numeral 500. Userinterface component 500 is presented to a workflow-building user inconnection with the workflow-building user having chosen to add workflowstep 414 of FIG. 4. FIG. 5A illustrates a step configuration modaldialog box that allows the workflow-building user to further configurethe workflow step associated with a function implemented by a hostedapplication. User input elements 502 and 504 correspond to the inputarguments of the function associated with the workflow step beingconfigured in connection with user interface component 500, which checksto see whether a particular Host is operational, or “up.” The firstargument is entitled “When someone says Host is up, you say . . . ” Insome embodiments, user input element 502 is a text box into which theworkflow-building user has input a thumbs-up emoji and the text “Ofcourse.” In one embodiment, the hosted application that exposes aparticular function provides default values for user input elements 502and 504.

In some embodiments, the workflow-building user may select either ofinsert a variable links 512 and 514 in order to provide a variableinstead of a constant string in connection with user input elements 502and 504. The configuration of user input elements 502 and 504 with avariable is further explained in connection with FIG. 5B below. Invarious embodiments, check box 516 is provided so that theworkflow-building user can specify whether the workflow step should beperformed synchronously. If check box 516, which is entitled “Wait forstep to complete before proceeding,” is checked the workflow step istreated as a synchronous step and workflow execution is blocked untilthe workflow step is completed. Alternatively, if the checkbox isunchecked, execution is not blocked while the workflow step is executed.In some embodiments, remove button 510, cancel button 508, and savebutton 506 are provided in user interface component 500. SelectingRemove button 510 removes the workflow step from the workflow. Cancelbutton 508 cancels the workflow step configuration operation, and Savebutton 506 saves changes made in connection with the workflow stepconfiguration operation.

Turning now to FIG. 5B, a user interface component for inserting avariable associated with arguments to a function in certain embodimentsof the invention is depicted and referred to generally by referencenumeral 550. User interface component 550 is presented to aworkflow-building user in connection with the workflow-building userhaving chosen to insert a variable in FIG. 5A. FIG. 5B illustrates an“insert a variable” modal dialog box that allows the workflow-buildinguser to specify a variable to be inserted in connection withconfiguration of the workflow step associated with a functionimplemented by a hosted application. In some embodiments, a listing ofpotential variables to insert associated with a group-basedcommunication system function and workflow are provided. In someembodiments, the variables to be inserted are associated with a shortcutassociated with the group-based communication system function beinginvoked, such exemplary shortcuts are illustrated in FIG. 5A asshortcuts 552 and 554. A variable associated with the functionimplementing the workflow step is illustrated as variable 556 entitled“status.” In some embodiments, right clicking (or providing a long-pressgesture) on one of the variables provides additional informationregarding the variable. Selecting the variable causes the modal dialogbox to be dismissed and inserts the variable into a respective userinput associated with a workflow step configuration user interfacecontrol such as user interface control 500 of FIG. 5A.

Operation of Embodiments of the Invention

Turning now to FIG. 6, a data flow diagram 600 for carrying outembodiments of the invention is depicted. Depicted in data flow diagram600 is event-based application development environment 602. In someembodiments, event-based application development environment 602 is madeup of a source code editor and various other source code developmenttools. In some embodiments, these tools are installed on a developerdevice such as developer device 202 of FIG. 2. Alternatively, theevent-based application development system can be hosted remotely and afront-end interface provided to a developer so that the developer caninteract with event-based application development environment 602.

In addition to event-based application development environment 602,depicted is also event-based application execution environment 604,which is an environment for executing one or more event-basedapplications. Event-based application execution environment 604 may behosted in a data center operated by an operator of a group-basedcommunication system. Alternatively, event-based application executionenvironment 604 may be hosted in a public or private cloud oron-premises in a data center operated by an enterprise that consumesservices from a group-based communication system but does not permithosting of a particular event-based application and associated dataoutside of a data center operated by the enterprise. In someembodiments, event-based application execution environment 604 is aserverless execution environment hosted in connection with a public orprivate cloud platform.

Data flow diagram 600 also depicts external event source 606, which isany source of events to potentially be consumed by an event-basedapplication, as described above with respect to FIG. 3. External eventsource 606 may be a user who inputs a message into a group-basedcommunication system channel. The user may enter a message directly intoa group-based communication system channel by inputting text or otherdata into a client interface associated with the group-basedcommunication system. The user may also cause an event to be generatedby clicking on an interactivity interface associated with the clientinterface by (for example) clicking a button in the interface orotherwise interacting with an interface associated with the group-basedcommunication system. External event source 606 may also be anevent-based application that generates one or more output events basedon one or more triggering events. External event source 606 may also bean external application such as a news source or a social media site.Group-based communication system 608 is also depicted as both a sourceand recipient of events within the data flow as well as an interface andexecution environment of group-based communication system workflow stepsas explained below.

Within the environment of data flow diagram 600, as shown in flow 610,an application developer may scaffold a new project or fetch code for anexisting project in the context of development of an event-basedapplication. In some embodiments, this data flows from event-basedapplication execution environment 604, as in the case where skeletonapplications are provided in a central location associated withevent-based application execution environment 604. This may also be thecase when, for example, a source code repository function is alsoprovided by event-based application execution environment 604. It isunderstood that external source code repositories (not shown) may alsobe utilized to provide source code control functionality for theapplication developer. Once the application developer has scaffolded askeleton application or fetched an existing project, the applicationdeveloper may debug or add functionality to the event-based application.In some embodiments, an emulator or simulation of an applicationexecution environment is provided in connection with the event-basedapplication development environment 602 such that the applicationdeveloper can iteratively develop the event-based application.Alternatively, any time a file is changed in a set of files associatedwith the event-based application, the event-based application isdeployed onto the event-based application execution environment 604.

Flow 612 illustrates this deploy and/or run instruction. In someembodiments, deploying an event-based application into event-basedapplication execution environment 604 involves creating an applicationif not already created based on an application configuration metadata.Alternatively, the application is updated based on updated applicationsource code and application configuration metadata. In some embodiments,if an application icon file associated with the event-based applicationhas changed since the last deployment, the application icon file ispreprocessed and uploaded to the application execution environment.Preprocessing involves centering and cropping the icon according toapplication icon sizing requirements such as icon file size anddimensions. In some embodiments, source code is bundled and uploaded tothe application execution environment hosting platform. If an executionenvironment associated with the event-based application has not yet beenprovisioned, the execution environment is provisioned. In someembodiments, an application container is built at flow 616 prior todeployment to an application execution environment.

At flow 618, the application developer creates and monitors debuggingevents to test the event-based application in the course of applicationdevelopment. This may involve using an API associated with thegroup-based communication system to implement an application testingsuite with predefined inputs and corresponding associated expectedoutputs. Once deployed, whether in development or production, theevent-based application receives events, processes them and producesoutputs corresponding to application logic implemented by theevent-based application.

Turning now to FIG. 7, an exemplary flow chart 700 for illustrating theoperation of a method in accordance with one embodiment of the inventionis depicted. In various embodiments, an application developer works in adevelopment environment to develop source code that provides the basisfor an event-based application. The application developer inputs sourcecode instructions and application metadata, such as applicationconfiguration parameters in application configuration files. In someembodiments, the source code instructions are provided in the form ofsource code files in a scripting language such as one of the languagesof the ECMAScript family of programming languages. In other embodiments,the source code instructions are provided in the form of uncompiled orpre-compiled source code in a compiled programming language. In someembodiments, the application configuration parameters are provided inthe form of YAML configuration files. In other embodiments, anothermarkup language (such as JSON or XML) is used. In some embodiments, datafiles that make up the application instructions and configurationparameters are packaged up into an archive for transmission as a singledata file. In some other embodiments, the files may be transmittedindividually to a hosting environment. At step 702, these applicationinstructions and configuration parameters are received. In someembodiments, the application instructions and configuration parametersare received by an intermediate processing program associated with thedevelopment environment, which may run on a development client device ofthe application developer, such as development device 202 of FIG. 2. Invarious embodiments, the application instructions are designed tooperate on certain events as the events are received in a group-basedcommunication system.

Next, at step 704, an application container is generated based on theapplication instructions and application configuration parameters. Asused herein, an application container is a unit of software thatpackages up code and dependencies, such as libraries, so the applicationcan be deployed seamlessly and reliably from one application executionenvironment to another. In some embodiments, an application containerimage is a lightweight, standalone, package of software andconfiguration metadata that includes everything needed to run theapplication given a particular container runtime. A container runtime isan execution environment that can run a particular category ofapplication containers. In some embodiments, an application container isa virtual machine image that can be executed in any virtual machineexecution environment.

Next, at step 706, the application container is deployed into anapplication execution environment. In some embodiments, the applicationcontainer is transferred over a network to a remote data center hostingeither a public or private cloud. In some testing environments, theexecution environment may be an application execution environmentresiding on the application developer's development device. In someembodiments, the application execution environment is hosted by anoperator of a group-based communication system, either in a data centeroperated by the operator of the group-based communication system oranother public or private cloud. In some other embodiments, theapplication execution environment is hosted on-premises in a data centeroperated by an enterprise that consumes services from a group-basedcommunication system but does not permit hosting of a particularevent-based application and associated data outside of a data centeroperated by the enterprise. In some embodiments, deployment of theapplication container also entails initiating execution of processesassociated with the event-based application. In this embodiment, theevent-based application listens at a webhook URL and port associatedwith a public IP address. In some other embodiments, the event-basedapplication is merely deployed and will not execute until a relevantevent is received at a group-based communication system.

Continuing to test 708, once the event-based application has beendeployed, a monitoring process determines whether an actionable eventhas been received in connection with one or more group-basedcommunication system channels associated with a group-basedcommunication system. In some embodiments, the criteria by which it maybe determined whether an actionable event has been received are based ona configuration of one or more triggers. A trigger may be a descriptionof an event that should be routed to a particular function associatedwith an event-based application, as generally described above withrespect to FIG. 3. If no actionable event is received the monitoringcontinues to wait for an actionable event to be received. If, at test708, an actionable event has been received, execution proceeds to step710.

At step 710, the actionable event is transmitted to an appropriatedeployed application container. In some embodiments, this involves thegroup-based communication system detecting that a trigger has occurredsuch that certain conditions associated with the trigger have beensatisfied by a message or other event that has taken place in connectionwith a group-based communication system. In some embodiments, this maybe the receipt of a message or other group-based communication objectreceived in a group-based communication system channel. Broadlyspeaking, an event described above with respect to FIG. 3 iscontemplated as being processed at step 710. In some embodiments, theevent is formatted by the group-based communication system as a JSONobject and transmitted to the event-based application by posting an HTTPtransmission to the webhook URL associated with the event-basedapplication. In these embodiments, the HTTP transmission is anindication that an actionable event has been received and that it shouldtrigger execution of the event-based application.

Next, at step 712, a group-based communication system receives aresponse responsive to the event transmitted in the previous step. Insome embodiments, the response is a composite output associated withfunctions contained within the event-based application and comprisingapplication logic associated with the group-based communication system.In some embodiments, execution of the application logic associated withthe event-based application will have effected various side effects,such as opening a video conference session or writing data to a datapersistence store.

Finally, at step 714, based on the response, a message is posted in arespective group-based communication system channel. In someembodiments, the posted message is itself an event that may triggerfurther processing in the event-based application or in anotherevent-based application. In some other embodiments, the posted messagemay contain interactive attributes that, when further acted upon byusers of the group-based communication system, cause further events totrigger further execution by one or more event-based applicationsassociated with the group-based communication system.

Many different arrangements of the various components depicted, as wellas components not shown, are possible without departing from the scopeof the claims below. Embodiments of the invention have been describedwith the intent to be illustrative rather than restrictive. Alternativeembodiments will become apparent to readers of this disclosure after andbecause of reading it. Alternative means of implementing theaforementioned can be completed without departing from the scope of theclaims below. Certain features and sub-combinations are of utility andmay be employed without reference to other features and sub-combinationsand are contemplated within the scope of the claims. Although theinvention has been described with reference to the embodimentsillustrated in the attached drawing figures, it is noted thatequivalents may be employed and substitutions made herein withoutdeparting from the scope of the invention as recited in the claims.

Having thus described various embodiments of the invention, what isclaimed as new and desired to be protected by Letters Patent includesthe following:
 1. One or more non-transitory computer-readable mediastoring computer-executable instructions that, when executed by at leastone processor, perform a method for hosting an application in connectionwith a group-based communication system, the method comprising:receiving, from a development environment, application instructions andapplication configuration parameters associated with the applicationcorresponding to processing steps to be performed in response to atleast one group-based communication system event, wherein the at leastone group-based communication system event is associated with agroup-based communication system channel of the group-basedcommunication system; building an application container based on theapplication instructions and the application configuration parameters;deploying the application container into a third-party cloud computingenvironment that is distinct from the group-based communication system;and in response to detecting the at least one group-based communicationsystem event in the group-based communication system channel of thegroup-based communication system: transmitting, from the group-basedcommunication system and to the application container deployed into thethird-party cloud computing environment, an indication comprising the atleast one group-based communication system event and metadata associatedwith the at least one group-based communication system event; based onthe indication, triggering execution by the third-party cloud computingenvironment of the application instructions, thereby generating anexecution result responsive to at least one group-based communicationsystem event; receiving, by the group-based communication system andfrom the application container deployed into the third-party cloudcomputing environment, the execution result; and posting, in thegroup-based communication system channel, a message based on theexecution result.
 2. The one or more non-transitory computer-readablemedia of claim 1, wherein a video conference session is initiated basedon the execution result.
 3. The one or more non-transitorycomputer-readable media of claim 1, wherein the message is posted in adifferent group-based communication system channel.
 4. The one or morenon-transitory computer-readable media of claim 1, wherein theapplication container is deployed responsive to a determination that adeploying user of the group-based communication system has authorizationto deploy cloud-based applications.
 5. The one or more non-transitorycomputer-readable media of claim 1, wherein execution of the applicationinstructions in response to the at least one group-based communicationsystem event further comprises: storing data, via a persistenceapplication programming interface, in a data persistence serviceaccessible to the third-party cloud computing environment.
 6. The one ormore non-transitory computer-readable media of claim 5, wherein storingdata in a data persistence service comprises storing data intopredefined portions of a data persistence table and causing furtherevents to be generated in the group-based communication system channelof the group-based communication system.
 7. The one or morenon-transitory computer-readable media of claim 1, wherein anadministrative interface associated with the application definesapplication programming interface access permissions based on anassociated network destination.
 8. A method for hosting an applicationin connection with a group-based communication system, the methodcomprising: receiving, from a development environment, applicationinstructions and application configuration parameters associated withthe application corresponding to processing steps to be performed inresponse to at least one group-based communication system event, whereinthe at least one group-based communication system event is associatedwith a group-based communication system channel of the group-basedcommunication system; building an application container based on theapplication instructions and the application configuration parameters;deploying the application container into a third-party cloud computingenvironment that is distinct from the group-based communication system;and in response to detecting the at least one group-based communicationsystem event in the group-based communication system channel of thegroup-based communication system: transmitting, from the group-basedcommunication system and to the application container deployed into thethird-party cloud computing environment, an indication comprising the atleast one group-based communication system event and metadata associatedwith the at least one group-based communication system event; triggeringexecution by the third-party cloud computing environment of theapplication instructions based on the indication to generate anexecution result responsive to at least one group-based communicationsystem event; receiving, by the group-based communication system andfrom the application container deployed into the third-party cloudcomputing environment, the execution result; and posting, in thegroup-based communication system channel, a message based on theexecution result.
 9. The method of claim 8, wherein a video conferencesession is initiated based on the execution result.
 10. The method ofclaim 8, wherein the message is posted in a different group-basedcommunication system channel.
 11. The method of claim 8, wherein theapplication container is deployed responsive to a determination that adeploying user of the group-based communication system has authorizationto deploy cloud-based applications.
 12. The method of claim 8, whereinexecution of the application instructions in response to the at leastone group-based communication system event further comprises: storingdata, via a persistence application programming interface, in a datapersistence service accessible to the third-party cloud computingenvironment.
 13. The method of claim 8, wherein storing data in a datapersistence service comprises storing data into predefined portions of adata persistence table and causing further events to be generated in thegroup-based communication system channel of the group-basedcommunication system.
 14. The method of claim 13, wherein anadministrative interface associated with the application definesapplication programming interface access permissions based on anassociated network destination.
 15. A system comprising at least oneprocessor and at least one non-transitory memory storing computerexecutable instructions that when executed by the at least one processorcause the system to carry out actions comprising: receiving, from adevelopment environment, application instructions and applicationconfiguration parameters associated with an application corresponding toprocessing steps to be performed in response to at least one group-basedcommunication system event, wherein the at least one group-basedcommunication system event is associated with a group-basedcommunication system channel of a group-based communication system;building an application container based on the application instructionsand the application configuration parameters; deploying the applicationcontainer into a third-party cloud computing environment that isdistinct from the group-based communication system; and in response todetecting the at least one group-based communication system event in thegroup-based communication system channel of the group-basedcommunication system: transmitting, from the group-based communicationsystem and to the application container deployed into the third-partycloud computing environment, an indication comprising the at least onegroup-based communication system event and metadata associated with theat least one group-based communication system event; triggeringexecution by the third-party cloud computing environment of theapplication instructions based on the indication to generate anexecution result responsive to at least one group-based communicationsystem event; receiving, by the group-based communication system andfrom the application container deployed into the third-party cloudcomputing environment, the execution result; and posting, in thegroup-based communication system channel, a message based on theexecution result.
 16. The system of claim 15, wherein a video conferencesession is initiated based on the execution result.
 17. The system ofclaim 15, wherein the message is posted in a different group-basedcommunication system channel.
 18. The system of claim 15, wherein theapplication container is deployed responsive to a determination that adeploying user of the group-based communication system has authorizationto deploy cloud-based applications.
 19. The system of claim 15, whereinexecution of the application instructions in response to the at leastone group-based communication system event further comprises: storingdata, via a persistence application programming interface, in a datapersistence service accessible to the third-party cloud computingenvironment.
 20. The system of claim 19, wherein storing data in a datapersistence service comprises storing data into predefined portions of adata persistence table and causing further events to be generated in thegroup-based communication system channel of the group-basedcommunication system.